home *** CD-ROM | disk | FTP | other *** search
Text File | 1988-02-22 | 3.9 KB | 86 lines | [TEXT/TPAS] |
- Flags Written By Eric Johnson
- A genuinely useful cmd 50/51 October 29, 1987
- Updated February 21, 1988
- ============================================================================
-
- Flags is a very short cmd 50/51 application that you set up as sort of an
- "intermediate" between Host and the cmd 50/51 application you wish to jump
- to. Flags will correct a few bugs from Host, like forgetting to write
- his SystemMsg read bits to the Userlog, and also forgetting to update the
- users security level and time limit in case you've validated him online.
- Flags will also write access of the program to your Callerlog if you desire.
- Flags now fixes the bug whereby host occasionally quits to the finder after
- executing an external program. A linefeed is no longer sent to the
- Callerlog, and a few blanks are written to the Callerlog before the access
- message so that the Callerlog Analyzer programs won't go into hysterics
- when they encounter something they don't comprehend.
-
- Here's sort of a schematic of how flags works...
-
- Host -> DungeonsFlags -> Dungeons -> Host
-
- instead of just
-
- Host -> Dungeons -> Host
-
- Instead of having Host jump to your application, for instance that wonderful
- online game Dungeons, you have Host jump to Flags, which in turn will jump
- to Dungeons when it's through doing it's thing with the Userlog. Since
- I have several online games on my BBS, I have a different flags program for
- each one. I've named them all different things so I can tell them apart,
- there is DungFlags (for Dungeons), ThingFlags for Thing, etc. I've been
- running Flags for close to a month now with no problems whatsoever.
-
- To set up flags do the following:
-
- 1> Put flags in the same folder as the application you wish to jump to.
- 2> Rename the flags application to something meaningful (DungFlags for
- instance if you're jumping to Dungeons).
- 3> Run ResEdit and change the following STR resources.
- a> 500 should be your path to the userlog. End with a colon!
- b> 501 should be path to the Host application. End with a colon!
- c> 502 should be full path and file name of the application to be
- run after flags is through. (Fido:BBS:Dung:Dungeons for instance).
- d> 503 If you want the time limit and clearance level to be written,
- the first character of this STR should be a 'Y' or a 'y'. Otherwise
- the time limit and user clearance will NOT be written to the Userlog.
- e> 504 If you want external application accesses written to the Callerlog,
- put a 'Y' or a 'y' as the first character of this STR. This only works
- if your Callerlog is written to a disk file, not to the printer.
- f> 505 is the name of the application for the callerlog. If you want
- the callerlog to say "External Application Dungeons Accessed" then
- put "Dungeons" here. If you want the full pathname here, put the full
- pathname. This STR is just for you to put whatever you like to be
- written to the Callerlog. Program execution does not depend on this
- STR at all.
- 4> That's it. You're all through now.
-
- I'd like to thank Pete Johnson for suggesting that Flags jump to another
- application rather than just returning to Host. I probably would have
- taken months to figure that one out on my own.
-
- Flags is free. It's on me. Please remember my name though (Eric Johnson).
- Maybe someday you can do me a favor, buy me a beer or something. Or maybe
- I'll write something someday and make it shareware, and you'll say "Oh! Eric
- Johnson wrote that. He gave me Dungeons and now Flags. I'll send my check
- right away". Hope the program helps you.
-
- And now a closing message....
-
- Hail to the victors valiant,
- Hail to the conquering heroes,
- Hail, Hail to Michigan, the leaders and best.
-
- Go Blue!
- ============================================================================
-
-
-
-
-
-
-
-
-
-
-